System and method for exporting data to web-based applications

ABSTRACT

A system and method is provided for exporting data from a client-server, collaborative application to a relational database and/or web based application. The method is implemented on a computing infrastructure and includes extracting unstructured rich text information hosted in a client-server, collaborative application. The method further includes converting the unstructured rich text information to XML files using a series of XML APIs. The method further includes transforming the XML files (data) to XHTML using reusable stylesheets unique to each type of unstructured rich text information, and utilizing the xHMTL in a web based application.

FIELD OF THE INVENTION

The invention generally relates to a method and system of exporting dataand, in particular, to a system and method of exporting data from aclient-server, collaborative application to a relational database and/orweb based application.

BACKGROUND

Web 2.0 describes changing trends in the use of World Wide Webtechnology. For example, Web 2.0 aims to enhance creativity, secureinformation sharing, collaboration and functionality of the World WideWeb. As such, Web 2.0 concepts have led to the development of web-basedcommunities including social networking sites, video sharing sites,wikis, blogs, etc.

The extra functionality provided by Web 2.0 depends on the ability ofusers to work with the data stored on servers. This can come aboutthrough forms in an HTML page, through a scripting-language. The Web 2.0also permits syndication of site content, which involves standardizedprotocols that permit end-users to make use of a site's data in anothercontext. Protocols that permit syndication include Extensible MarkupLanguage (XML) based formats such as, for example, RSS (Really SimpleSyndication), Resource Description Framework (RDF) and Atom. The XML isa general-purpose specification for creating custom markup languages.The primary purpose of XML is to help information systems sharestructured data, particularly via the World Wide Web and Web 2.0applications. By adding semantic constraints, application languages canbe implemented in XML, e.g., XHTML amongst thousands of others.

The Web 2.0 supports many types of web services A web service is asoftware system designed to support interoperable machine-to-machineinteraction over a network. The web service definition encompasses manydifferent systems, but in common usage the term refers to clients andservers that communicate over the HTTP protocol used on the World WideWeb. One such service uses XML messages that follow the SOAP standard.

Currently, tools can export data from one application to anotherapplication which may be helpful for exporting content to Web 2.0applications. For example, tools are known to extract HTML contentstored in relational databases to Web 2.0 applications. However, thesetools lack an intuitive way to map specialized content stored in richtext fields like file attachment metadata, collapsible sections, tabbedtables and hotspot/links used by, for example, Lotus Domino®. (LotusDomino is a registered trademark of International Business MachinesCorporation in the United States and throughout the world.) Lotus Dominois a server product that provides enterprise-grade e-mail, collaborationcapabilities, and custom application platform. Domino can be used as anapplication server for Lotus Notes applications and/or as a web server.

Accordingly, there exists a need in the art to overcome the deficienciesand limitations described hereinabove.

SUMMARY

In a first aspect of the invention, a method implemented on a computinginfrastructure comprises extracting unstructured rich text informationhosted in a client-server, collaborative application. The method furthercomprises converting the unstructured rich text information to XML filesusing a series of XML APIs. The method further comprises transformingthe XML files (data) to XHTML using reusable stylesheets unique to eachtype of unstructured rich text information, and utilizing the xHMTL in aweb based application.

In another aspect of the invention, a computer program product comprisesa computer usable storage medium having readable program code tangiblyembodied in the storage medium. The computer program product is operableto: extract data from unstructured information using a series of XMLAPIs; convert the extracted data into XML files; and transform the XMLfiles into XHTML documents using unique stylesheets for each type ofunstructured information.

In another aspect of the invention, a system for web applicationscomprises: first program instructions to extract XML files fromunstructured rich text information; second program instructions totransform the XML files to XHTML files using reusable tailoredstylesheets associated with specific extracted XML files; and thirdprogram instructions to save the XHTML files in a relational databaseand/or for use in a web application. A computer readable media storesthe first, second and third program instructions. A central processingunit executes the first, second, third and fourth program instructions.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 shows an illustrative environment for implementing processes inaccordance with the present invention;

FIG. 2 shows an exemplary architect implementing aspects of the presentinvention;

FIG. 3 is a flow diagram showing a program control creating stylesheetsin accordance with aspects of the present invention; and

FIG. 4 is a flow diagram showing a program control convertingunstructured information in accordance with aspects of the presentinvention.

DETAILED DESCRIPTION

The invention generally relates to a method and system of exporting dataand, in particular, to a system and method of exporting data from aclient-server, collaborative application to a relational database and/orweb based application. In implementation, the present invention solvesmany practical issues that otherwise have curtailed the realization ofexporting rich content from Domino or Lotus Notes. More specifically,the present invention provides a mechanism to extract content hosted inLotus Notes databases to web browsers via a Java-based API. For example,the present invention is configured to exported data as XML files (data)and place such data on either File Systems or relational databasemanagement systems (RDMS) with XML capabilities such as, for example,DB2 (version 9). DB2 is part of a family of RDMS of InternationalBusiness Machine.

Advantageously, the invention provides a tool that is capable ofconverting various format features of a Lotus Domino database to anotherdatabase format. In particular, the tool is configured to convert DominoRich Text Elements like “tabs”, “twisties”, tables, collapsiblesections, as well as other Rich Text Elements to a format exportable toa relational database. To make the conversion, a “stylesheet” issupplied to a known transformation engine such as, for example, an XMLtransformation engine using Domino XML APIs. The translation engineimplements the “stylesheet” which, in turn, provides the conversiontranslation for exportation into a relational database. The relationaldatabase can be, for example, a DB2 relational database maintained,supported, and supplied by International Business Machine Corporation.

The exported data from Lotus Notes database can now be data accessibleto J2EE applications such as, for example, Web 2.0 applications. Inembodiments, the Domino data is exposed to Web 2.0 rest-based webservices and J2EE applications. In this way, it is now possible forusers gain easy access to Domino store data by using the mechanismpresented in the present invention while preserving much of the contentformat and metadata.

Exemplary System Environment and Infrastructure

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer-usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,device, or propagation medium. More specific examples (a non-exhaustivelist) of the computer-readable medium would include the following:

-   -   a portable computer diskette,    -   a hard disk,    -   a random access memory (RAM),    -   a read-only memory (ROM),    -   an erasable programmable read-only memory (EPROM or Flash        memory),    -   a portable compact disc read-only memory (CDROM), and/or    -   an optical storage device.

In the context of this document, a computer-usable or computer-readablemedium may be any medium that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device. The computer usableprogram code may be transmitted using any appropriate transmission mediavia a network.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork. This may include, for example, a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

FIG. 1 shows an illustrative environment 10 for managing the processesin accordance with the invention. To this extent, the environment 10includes a server 12 that can perform the processes described hereinusing the computer program code. In particular, the server 12 includes acomputing device 14. The computing device 14 can be resident on anetwork infrastructure of any third party service provider (any of whichis generally represented in FIG. 1). The computing device 14 and/or theserver 12 includes a transformation engine 40 and XML API 50. Inembodiments, the XML API 50 may be resident on a Domino (Lotus) server(which can be representative of the infrastructure shown in FIG. 1.)

In implementation, the content of unstructured information such as, forexample buttons, figures, tabs, collapsible sections, etc. isextracted/exported from a Domino database through a series of Domino XMLexports using the XML API 50. In this way, the content of theunstructured information can be converted to XML files (data). The XMLfiles (data) and any file attachments are saved in file systems or arelational database such as, for example, the storage system 22B ofFIG. 1. Thus, in embodiments, data is exported as XML files (data) andplaced on either file systems or relation database system with XMLcapabilities like DB2. File attachments are exported as binary objectsand stored in BLOGS (binary large objections) in the relationaldatabase; whereas the XML data is stored in CLOBS (common largeobjects). In embodiments, a unique ID may be provided for each documentand file attachment, making it possible to match the appropriate XMLfile with the corresponding file attachment.

In embodiments, the transformation engine 40 transforms the XML files(data) into XHTML files using stylesheets unique to each type ofunstructured information. That is, the Lotus Notes document formattingand metadata is preserved using tailored stylesheets and the Domino XMIAPI. The Lotus notes document content is stored in XHTML making veryaccessible for downstream use by J2EE applications and Web 2.0 REST webservices.

The stylesheets are designed to be unique for each type of unstructuredinformation such as, for example, collapsible sections, tabbed tables,etc. These stylesheets are designed to be reusable in order to providean intuitive way to map specialized content stored in rich text fieldslike file attachment metadata, collapsible sections, tabbed tables andhotspot/links used by, for example, Lotus Domino®.

In embodiments, the stylesheets are uniquely defined and can be storedin a database such as, for example, a storage system depicted in FIG. 1.The unique identification for each stylesheet allows easy access andretrieval by the transformation engine 40 in order to convert the rawdata (XML unstructured information). The stylesheet can be identified inmany different ways such as, for example,

-   -   1. Embedded in the input message: This can be accomplished by        specifying a name in the input message body, include an        XML-stylesheet processing instruction, which is specified by the        XML standard, in the input message body.    -   2. Specified in the local environment message tree: This can be        accomplished by specifying a stylesheet name in the local        environment by using a preceding Compute node to define the        local environment variable    -   3. Specified in the Stylesheet property GUI interface: This can        be accomplished by filling in the Stylesheet        Directory/Stylesheet Name properties in the interface. The node        will concatenate the values of these two properties and treat it        as a reference to a file in the file system.

By way of non-limiting illustrative example, a contemplated stylesheetfor a tabbed table may include the following exemplary code:

  function tab(tableId,rowId) {    tableElement=document.getElementById(tableId);     childCount =tableElement.childNodes.length;     for(var i=0;i<xsl:textdisable-output- escaping=“yes”>&lt;</xsl:text>childCount;i++){      if(tableElement.childNodes[i].tagName == “TBODY”){         //TODOmake sure there is only one TBODY         var tbody =tableElement.childNodes[i];         var tbodyChildCollection =tbody.childNodes;         for(var j=0;j<xsl:text disable-output-  escaping=“yes”>&lt;</xsl:text>tbodyChildCollection.length;j++){          if(tbodyChildCollection[j].tagName == “TR”){             varrow=tbodyChildCollection[j];             var id=row.getAttribute(‘id’);            if(id==rowId){               row.style.display=“”;            }             else{               row.style.display=“none”;            }           }         }       }     }   }

By way of non-limiting illustrative example, a contemplated stylesheetfor collapsible section may include the following exemplary code:

<xsl:template match=“dxl:section”>     <xsl:variable name=“myid”select=“generate-id(.)”/>     <xhtml:p>         <xsl:attributename=“class”><xsl:text>id</xsl:text><xsl:value-ofselect=“dxl:sectiontitle/@pardef”/><xsl:text></xsl:text></xsl:attribute>    <xsl:for-each select=“dxl:sectiontitle”>       <xhtml:spanonclick=“consatina2(‘{$myid}d’,‘{$myid}i’)” id=“{$myid}i”>        <xsl:attribute name=“style”>float:left;<xsl:apply- templatesselect=“dxl:font” mode=“font-to-css”/></xsl:attribute>        <xsl:attribute name=“class”>expand-link- dark</xsl:attribute>        <xsl:choose>           <xsl:when test=“*|text( )”>            <xsl:apply-templates select=“*|text( )”/>          </xsl:when>           <xsl:otherwise>            <xsl:text>&#160;</xsl:text>           </xsl:otherwise>        </xsl:choose>       </xhtml:span>       <xhtml:divstyle=“clear:both”></xhtml:div>     </xsl:for-each>     <xhtml:spanid=“{$myid}d”>       <xsl:attribute name=“style”><xsl:textdisable-output- escaping=“yes”>display:none</xsl:text></xsl:attribute>        <xsl:apply-templates/>     </xhtml:span>     </xhtml:p>  </xsl:template>

The transformation engine 40 can be, for example, a WebSphere® MessageBroker XSL transformation engine. (WebSphere is a registered trademarkof International Business Machines Corporation in the United States andthroughout the world.) The XSL transformation (XSLT) is astandards-based technology that transforms XML documents into XHMTLdocuments. Transformation rules for the input XML documents aredescribed in Extensible Stylesheet Language (XSL), which is itself inXML. The XSL transformation rules reside in the stylesheet.

In embodiments, the converted XHTML is saved in a relational databasewith the unique file attachments. In embodiments, the XHMTL is saved asCLOBS (common large objects) and the file attachments are saved as BLOGS(binary large objects). These CLOBS and BLOGS can then be used for J2EEand Web 2.0 applications.

The computing device 14 also includes a processor 20, memory 22A, an I/Ointerface 24, and a bus 26. The memory 22A can include local memoryemployed during actual execution of program code, bulk storage, andcache memories which provide temporary storage of at least some programcode in order to reduce the number of times code must be retrieved frombulk storage during execution. In addition, the computing deviceincludes random access memory (RAM), a read-only memory (ROM), and aCPU. The computing device 14 also includes an I/O device 28. The I/Odevice 28 can be, for example, any device that enables an individual tointeract with the computing device 14 or any device that enables thecomputing device 14 to communicate with one or more other computingdevices using any type of communications link. The external I/Odevice/resource 28 may be for example, a display of a computing devicesuch as a personal digital assistant (PDA).

In general, the processor 20 executes computer program code, which isstored in the memory 22A and/or storage system 22B. While executing thecomputer program code, the processor 20 can read and/or write datato/from memory 22A, storage system 22B, and/or I/O interface 24. Theprogram code executes the processes of the invention. The bus 26provides a communications link between each of the components in thecomputing device 14.

The computing device 14 can comprise any general purpose computingarticle of manufacture capable of executing computer program codeinstalled thereon (e.g., a personal computer, server, etc.). However, itis understood that the computing device 14 is only representative ofvarious possible equivalent-computing devices that may perform theprocesses described herein. To this extent, in embodiments, thefunctionality provided by the computing device 14 can be implemented bya computing article of manufacture that includes any combination ofgeneral and/or specific purpose hardware and/or computer program code.In each embodiment, the program code and hardware can be created usingstandard programming and engineering techniques, respectively.

Similarly, the server 12 is only illustrative of various types ofcomputer infrastructures for implementing the invention. For example, inembodiments, the server 12 comprises two or more computing devices(e.g., a server cluster) that communicate over any type ofcommunications link, such as a network, a shared memory, or the like, toperform the process described herein. Further, while performing theprocesses described herein, one or more computing devices on the server12 can communicate with one or more other computing devices external tothe server 12 using any type of communications link. The communicationslink can comprise any combination of wired and/or wireless links; anycombination of one or more types of networks (e.g., the Internet, a widearea network, a local area network, a virtual private network, etc.);and/or utilize any combination of transmission techniques and protocols.

In embodiments, the invention provides a business method that performsthe steps of the invention on a subscription, advertising, and/or feebasis. That is, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. In return, the service provider can receivepayment from the customer(s) under a subscription and/or fee agreementand/or the service provider can receive payment.

Exemplary Architecture

FIG. 2 shows an exemplary architecture in accordance with aspects of theinvention. In particular, FIG. 2 shows a mechanism to extract contenthosted in Lotus Notes databases to web browsers (for Web 2.0applications) via a Java based API (XML API). Data is exported as XMLfiles (data) and placed on either file systems or relational databasesystem with XML capabilities like DB2. The Lotus Notes documentformatting and metadata is preserved using tailored stylesheets and theDomino XMI API. File attachments are sported as binary objects andstored in BLOGS in the relational database.

In particular, FIG. 2 shows a web browser 200. The web browser 200provides an http request to a load balancer 205. The load balancer 205is an IP sprayer, which is configured to handle multiple requests. Thehttp request is passed from the load balancer 205 to a net-cache proxy210. The net-cache proxy 210 is a machine used to cache frequentrequested files. The net-cache proxy 210 can provide information relatedto the request back to the web browser 200. The net-cache proxy 210 alsopasses the request to the load balance 215 in Zone 2. This request canthen be passed to a portal server (e.g., WebSphere Portal Server) 220.In embodiments, the WebSphere Portal Server 220 is a cluster of twonodes, for example.

The portal server 220 communicates with a DB2 production server 230,which is a server running DB2 production. Information is passed betweenthe DB2 production server 230 and the staging DB2 Server 235. The DB2staging server 235 is a server running DB2 The portal server 220 alsocommunicates with an LDAP 240. The LDAP 240 (Lightweight DirectoryAccess Protocol) is an application protocol for querying and modifyingdirectly services running over TCP/IP. More specifically, the LDAP 240is an Internet protocol that email and other programs use to look upinformation from the server 220. In embodiments, the LDAP represents thedirectory used for authentication and authorization of users of thepresent invention (e.g., IBM Directly Server). The DB2 server 235 alsocommunicates with a JAVA Server 245. The JAVA server 245 is a serverrunning JAVA programs, which passes XHTML from the DB2 server 235 andNotes Database 250.

Exemplary Processes

FIGS. 3 and 4 illustrate exemplary processes in accordance with thepresent invention. The steps of FIGS. 3 and 4 may be implemented on thecomputer infrastructure of FIG. 1 and/or the architecture of FIG. 2, forexample. The flow diagrams in FIGS. 3 and 4 may be illustrative of thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each process mayrepresent a module, segment, or portion of code, which comprises one ormore executable instructions for implementing the specified logicalfunction(s). It should also be noted that, in some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. Each block of the flow diagrams and combinationsof the flow diagrams illustrations can be implemented by special purposehardware-based systems that perform the specified functions or acts, orcombinations of special purpose hardware and computer instructionsand/or software, as described above.

Additionally, the invention can take the form of an entirely hardwareembodiment, an entirely software embodiment or an embodiment containingboth hardware and software elements. Software includes but is notlimited to firmware, resident software, microcode, etc. Furthermore, theinvention can take the form of a computer program product accessiblefrom a computer-usable or computer-readable medium providing programcode for use by or in connection with a computer or any instructionexecution system. The software and/or computer program product can beimplemented in the environment of FIG. 1. For the purposes of thisdescription, a computer-usable or computer readable medium can be anyapparatus that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device. The medium can be an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system (orapparatus or device) or a propagation medium. Examples of acomputer-readable medium include a semiconductor or solid state memory,magnetic tape, a removable computer diskette, a random access memory(RAM), a read-only memory (ROM), a rigid magnetic disk and an opticaldisk. Current examples of optical disks include compact disk-read onlymemory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.

FIG. 3 shows a flow diagram depicting the creation of stylesheets. Atstep 300, the program control creates a stylesheet for a uniqueunstructured information such as, for example, buttons, collapsiblesections, etc. At step 305, the program control provides the stylesheetwith a unique identification for later retrieval. At step 310, theprogram control saves the stylesheet in a storage system such as adatabase or other file system. At step 315, the program control makes adecision as to whether any additional stylesheets need to be created. Ifnot, the process ends at step 320. If any additional stylesheets arerequired, the process continues to step 300.

FIG. 4 is a flow diagram showing a process of converting unstructuredinformation in accordance with aspects of the present invention. Morespecifically, at step 400, unstructured information is extracted andconverted to XML data using XML API. At step 405, the program controlmakes a determination as to whether there are any file attachmentsassociated with the XML files (data). If not, the process continues tostep 420. If there are file attachments, at step 410, the programcontrol matches the XML file with the file attachments. At step 415, theprogram control provides a unique ID to the match so that it can laterbe retrieved for use in a Web 2.0 or J2EE application. At step 420 andstep 425, the program control selects a stylesheet for the particularfunction, e.g., collapsible section, etc., and using the selectedstylesheet the transformation engine transforms the XML to XHTML. Atstep 430, the program control saves the XHTML in a relational databaseand/or used in a J2EE or Web 2.0 application.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims, if any, are intendedto include any structure, material, or act for performing the functionin combination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated. While the invention has been described interms of embodiments, those skilled in the art will recognize that theinvention can be practiced with modifications and in the spirit andscope of the appended claims.

1. A method implemented on a computing infrastructure comprising:extracting unstructured rich text information hosted in a client-server,collaborative application; converting the unstructured rich textinformation to XML files using a series of XML APIs; transforming theXML files (data) to XHTML using reusable stylesheets unique to each typeof unstructured rich text information; and utilizing the xHMTL in a webbased application.
 2. The method of claim 1, wherein the rich textinformation is at least one of collapsible sections, tabs, twisties andtables.
 3. The method of claim 1, wherein the client-server,collaborative application is a Domino/Lotus Notes application.
 4. Themethod of claim 1, wherein original formatting of the unstructured richtext information is preserved using the unique reusable stylesheets. 5.The method of claim 1, wherein the web based application is one of aJ2EE application and Web 2.0 REST web service.
 6. The method of claim 1,further comprising: exporting file attachments; matching the fileattachments to respective converted XML files; and providing a unique IDfor each of the matching to provide a mechanism for later retrieval. 7.The method of claim 6, wherein the file attachments are binary objectsstored as BLOGS (binary large objections) and the XML files are commonobjects stored in CLOBS (common large objects).
 8. The method of claim1, wherein the XML files are placed on file systems or a relationaldatabase with XML capabilities.
 9. The method of claim 1, wherein thetransforming is performed by a transformation engine.
 10. The method ofclaim 1, wherein the steps provided on the computing infrastructurewhich is at least one of maintained, deployed, created and supported bya service provider.
 11. The method of claim 1, wherein the steps areprovided on a software component, a hardware component or a combinationof the software component and the hardware component on the computinginfrastructure.
 12. A computer program product comprising a computerusable storage medium having readable program code tangibly embodied inthe storage medium, the computer program product being operable to:extract data from unstructured information using a series of XML APIs;convert the extracted data into XML files; and transform the XML filesinto XHTML documents using unique stylesheets for each type ofunstructured information.
 13. The computer program product of claim 12,wherein the computer program product is further operable to store theXHTML documents into a relational database.
 14. The computer programproduct of claim 13, wherein the computer program product is furtheroperable to store to store file attachments as BLOGS.
 15. The computerprogram product of claim 12, wherein the computer program product isfurther operable to match the file attachments with appropriate of theXHTML documents.
 16. The computer program product of claim 15, whereinthe computer program product is further operable to store the uniquestylesheets with a unique ID for later retrieval.
 17. The computerprogram product of claim 15, wherein the computer program product isprovided on a computing infrastructure which is at least one ofmaintained, deployed, created and supported by a service provider.
 18. Asystem for web applications comprising: first program instructions toextract XML files from unstructured rich text information; secondprogram instructions to transform the XML files to XHTML files usingreusable tailored stylesheets associated with specific extracted XMLfiles; and third program instructions to save the XHTML files in arelational database or for use in a web application; a computer readablemedia which stores the first, second and third program instructions; anda central processing unit to execute the first, second, third and fourthprogram instructions.
 19. The system of claim 18, wherein the computerinfrastructure is at least one of supported, deployed, maintained, andcreated by a service provider.
 20. The system of claim 18, wherein thesteps are provided on a software component, a hardware component or acombination of the software component and the hardware component.